👈 Launch a Binder on branch brichet/jupytergis/layers

My comments are only nitpicky comments about the naming of layersTree. It seems a bit heterogeneous in the code-base between layersTree, layerTree and treeLayers so I'm suggesting going for layersTree everywhere.

Your are right for some of them, but maybe not for all.
I wanted to make the distinction between the tree itself (a IJGISLayerGroup object, what I called layerTree), and the list of layers coming from the tree (a (IJGISLayerGroup | string)[] object, that I called treeLayers).

The second come from the fact that I used a IJGISLayerGroup for the tree but we only need the list of layers, the other properties are useless. See #4 (comment) for reference.

Maybe we should declare the tree as a (IJGISLayerGroup | string)[] to simplify.
The only drawback is the duplication of the following schema, for the layersTree itself and the layers of a IJGISLayerGroup.

"items": {
  "oneOf": [
      {"type": "string"},
      {
        "type": "object",
        "$ref": "#/definitions/jGISLayerGroup"
      }
  ]
}

It would clarify the naming and the tree object, avoiding useless properties, since the tree should only be a list of layers and groups (if I'm not mistaken).

Oh ok I see.

Maybe we should declare the tree as a (IJGISLayerGroup | string)[] to simplify

That sounds good to me. Then you only operate on this layersTree (the root) which is of this type.

Oh ok I see.

Maybe we should declare the tree as a (IJGISLayerGroup | string)[] to simplify

That sounds good to me. Then you only operate on this layersTree (the root) which is of this type.

Exact, let's update it then.

@martinRenou I updated the schema